System and method for searching data partially displayed on a user interface

ABSTRACT

The present invention includes systems and methods for customization of internet applications. Multiple levels of customization are applied to both static and functional aspects of user interface elements including, for example, tab-order, tab-over, immediate access keys, and hotkeys. Customization is also achieved with respect to searching over multiple user interfaces, presentation of information on a user interface, and the interaction model used by the internet application. Customization is enabled on any client supporting standard browser functionality.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority from commonly owned U.S. ProvisionalPatent Application No. 60/273,190 entitled “HTML—Based Applications forSupport of Complex Transactions,” filed Mar. 2, 2001 and U.S.Provisional Patent Application No. 60/316,773, entitled “Meta LanguageControl of Complex Network Applications,” filed Aug. 31, 2001. Thedisclosures of these two provisional patent applications areincorporated herein by reference.

This application is related to co-pending U.S. patent application Ser.No. 10/040,397, entitled “Customization of Tab-order Functionality inInternet Applications,” co-pending U.S. patent application Ser. No.041,034, entitled “Customization of Client-Server Interaction in anInternet Application,” co-pending U.S. patent application Ser. No.10/035,413, entitled “Customization of Immediate Access and HotKeyFunctionality in an Internet Application User Interface,” co-pendingU.S. patent application Ser. No. 10/165,623, entitled “System and Methodfor Automatic Generation of HTML Based Interfaces Including AlternativeLayout Modes,” and co-pending U.S. patent application Ser. No.10/041,015, entitled “Customization of User Interface Presentation in anInternet Application User Interface.”

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable

BACKGROUND

1. Field of the Invention

The invention is in the field of application program development andspecifically in the field of development and customization of internetapplications.

2. Description of the Prior Art

In current internet design practice the elements, layout, andfunctionality of user interfaces and associated web pages are intendedfor casual users. These users typically access applications on anirregular basis and therefore prefer a simple and intuitive interfaceover more powerful alternatives. This preference has lead to the nearuniversal adoption of a basic point and click interaction model in whichnavigation and control is accomplished by selecting user interfaceelements with a pointing device such as a mouse. Current design practiceis also limited by outdated conceptions related to bandwidth limitationsand portability. The point and click interaction model became dominateduring a period of more limited bandwidth than is currently available.Similarly, the range of devices used to access user interfaces has grownsignificantly. Further, many of the new devices have limited memory andprocessing power.

Current internet design practice and the associated philosophy aredetrimental to the development and use of enterprise applicationprograms in an internet setting. These programs are typically used byconsistent users who interact with the application on a regular basisand prefer an interface optimized for the most efficient interaction.Consistent users, therefore, desire features and capabilities beyondthose encompassed by current internet design practice. For example,application programs designed for use on a standalone computer typicallydepend on a keyboard based interaction model. In contrast with the mousebased point and click model favored on the internet, the keyboard basedinteraction model primarily depends on keystrokes entered by a user tocommunicate to the application. Utilizing keystrokes can be moreefficient than the basic point and click interaction model. Forinstance, in data entry applications, where a user prefers to keep hisor her hands located on the keys, having to reach for and manipulate amouse is often a significant source of distraction and delay.

A desire to accommodate the greatest number of users has focused currentinternet design practice towards satisfying casual and/or novice usersinstead of consistent users. The resulting designs are intuitivelysimple to use but less powerful or efficient than they would be ifcustomized for each enterprise or personalized for each individual user.Unfortunately, in the prior art, the ability to customize an internetbased application is severely limited.

Current customization capabilities are generally a function ofapplication architecture. The available architectures includestandalone, client/server, and internet configurations. Standaloneapplications are the simplest, having just one user operating on onecomputing device. Standalone applications also typically have fullaccess to the computing device for the purposes of storing and accessingconfiguration data. Client/server applications include both a client anda server. The application is primarily based on a server system but alsorelies on client system resources such as processing, memory, and datastorage. In order to access these resources some part of the applicationresides on the client. Customization of client/server applicationsdepends on these resources and may also require additionalcommunications between the server and the client.

In contrast to the client/server architecture, pure internetapplications use a standard web browser or browser compatible device astheir client, and are generally referred to as thin or small clientfootprint applications. The internet application architecture providesan advantage in that no application code, other than the browser, needbe installed or maintained on the client. Internet applications usingstandard internet protocols and security mechanisms do not requirespecialized client side code specific to the internet application andplace essentially all the processing-intensive activities on an internetserver.

Customization of internet applications that depend on a browser orbrowser compatible thin client is limited in the prior art to selectionand layout of predefined elements on a user interface. These predefinedelements include buttons, links, fields, forms, graphics, text, andother distinct parts of a user interface or associated web page. Forexample, some websites allow a user to design a “personal” web page orchoose which news stories should appear on a page and how they should bearranged. Beyond appearance and location of custom text, URLs, orgraphics, these websites do not allow customization of the predefinedelements themselves. Thus, there are no means available by which a usercan customize the functional properties of a user interface element.

Functional properties of a user interface element include operationsbeyond basic point and click navigation and retrieval of further contentusing a URL. These properties are important to consistent users. Forexample, they determine the interaction model between the user and anyunderlying applications. Customizing and personalizing functionality is,therefore, important to meeting the needs of consistent users. Theinability to fully customize or personalize internet applications is alimitation of current design practice and has discouraged theimplementation of enterprise application programs as internetapplications.

Traditional client/server applications have included customization ofelements within the application user interface. However, thiscustomization of element functionality requires additional installed orbuilt-in client-side code (e.g., Java® code, ActiveX®, etc.) on theclient system. With the inclusion and execution of this client-side codethe application is not a purely HTML based internet application. Inaddition to issues such as download security, licensing requirements,support, and compatibility, client-side code is disadvantageous becauseit is dependent on the client environment. This environment includescritical factors and limitations such as available memory, underlyingoperating system type (Windows®, UNIX, etc.), and operating systemfeatures. Client-side code also reduces portability because itsexecution may require computing power beyond what is available in someinternet access devices. The amount of required client-side code andcomputing power required for a client/server application increases withthe size and functionality of the application.

The client/server architecture has also been used to internet enablenon-web based applications. In this process a client-side interface isused to access Windows®, UNIX, or Linux applications that are executedon a server. The client-side interface is either a custom application ora browser to which proprietary extensions have been added. The interfacefunctions as a remote terminal accessing a pre-existing application.Interaction between the interface and the server-side application iscontrolled by computer code (i.e. ActiveX or Java code) downloaded orotherwise installed on the client. This client-side computer code issubject to the disadvantages of the traditional client/serverarchitecture, such as dependence on the client side environment, etc.

Conventional standalone or “client side” applications are executed on asingle computer with full access to the resources of the computer'soperating system. These resources include a wide variety ofpersonalization tools that are not available in browser-basedenvironments. For example, a computer's operating system includesenvironmental settings (in registry and system files) that can beaccessed and modified by executing programs. Standalone applications canalso access and save files, including personalization data, on localdrives. These resources are used to provide a high degree ofcustomizability to standalone applications. Unfortunately, theseresources and the personalization utilities that depend on them are notdirectly portable to browser based environments. For example, securityprotocols prevent server side applications from reading and writing tofiles larger than a cookie on a client system. The degree ofpersonalization found in large standalone applications requires accessto template and registry files at a frequency that is currentlyimpractical and generally undesirable in an internet environment. Inaddition, this approach results in personalization restricted to theindividual user or client level.

The limitations of thin clients have prevented the implementation oftrue internet enterprise applications and the relative perspective ofthe standalone and client/server environments likewise prevented eventheir consideration for this purpose. Features important toimplementation of enterprise solutions, such as customization offunctionality and transformation to a keyboard based interaction model,are simply not available in prior art internet applications.

SUMMARY OF THE INVENTION

The present invention includes systems and methods for customization ofinternet applications and their associated user interfaces in a browserbased environment. The user interfaces are typically delivered to a useras a web page or part thereof. The customization applies to both staticand functional aspects of user interface elements.

One embodiment of the present invention includes a customizableapplication system comprising an internet application system configuredto support an internet application, the internet application associatedwith metadata configured for generating an application user interfaceincluding a plurality of user interface elements having a tab-orderproperty, the internet application system including both an applicationserver configured to generate the application user interface and a webapplication server configured to deliver the application user interfaceto a client. The embodiment further includes a personalization systemwith a personalization engine and a user profile interface, thepersonalization interface configured to modify personalization datacharacterizing the tab-order property such that the tab-order of theplurality of user interface elements is modified, and a data repositoryincluding a data record for storing the personalization data, the datarecord being accessible using the metadata.

One embodiment of the present invention includes a method of developinga customizable user interface element by developing a user interfaceelement including the property, determining a data record for holding avalue used to characterize the property, the data record being stored ina data repository and being user modifiable, the data repository beingphysically remote from a client used to display an application userinterface, generating metadata defining the property, the metadataincluding a reference to the data record, and storing the metadata inassociation with the user interface element, the user interface elementbeing configured for inclusion in the application user interface.

One embodiment of the present invention includes a method of customizingan application user interface by accessing a page definition, the pagedefinition including metadata associated with a customized property of auser interface element, accessing the metadata to obtain a reference toa data record, using the reference to access the data record, the datarecord being stored in a data repository and being user modifiable, thedata repository being physically remote from a client used to display anapplication user interface, accessing the data record to determine avalue defining the customized property, generating markup-languageresponsive to the determined value, and including the generatedmarkup-language in the application user interface.

One embodiment of the present invention includes a customizableapplication system comprising an internet application system configuredto support an internet application, the internet application associatedwith metadata configured for generating an a plurality of applicationuser interfaces each having customizable interaction model, the internetapplication system including both an application server configured togenerate the application user interface and a web application serverconfigured to deliver the application user interface to a client. Theembodiment further includes a personalization system including apersonalization engine and a user profile interface, the personalizationinterface configured to modify personalization data characterizing theinteraction model such that the interaction model in more than one ofthe plurality of application user interfaces is modified, and a datarepository including a data record for storing the personalization data,the data record being accessible using the metadata.

One embodiment of the present invention includes a method of developinga customizable application user interface associated with an internetapplication by selecting a customizable interaction model associatedwith a data record, the data record being stored in a data repositoryand being user modifiable, the data repository being physically remotefrom a client used to display the application user interface, includingthe interaction model in the application user interface, generatingmetadata associated with the interaction model, the metadata including areference to the data record, and storing the metadata in associationwith the internet application, the internet application being configuredfor access using the application user interface.

One embodiment of the present invention includes a method of customizingan application user interface by accessing a page definition, the pagedefinition including metadata associated with a customized property of ainteraction model, accessing the metadata to obtain a reference to adata record, using the reference to access the data record, the datarecord being stored in a data repository and being user modifiable, thedata repository being physically remote from a client used to display anapplication user interface, using information read from the data todetermine a value defining the customized property, generatingmarkup-language responsive to the determined value, and including thegenerated markup-language in the application user interface.

An embodiment of the present invention includes a customizableapplication system comprising an application server, an applicationinterface generator configured to generate an application userinterface, the application user interface including a customizableimmediate access keystroke sequence and configured as an interfacebetween the application server and a client, a web application serverconfigured to deliver the application user interface to a client, meansfor specifying customization data configured to characterize thecustomizable immediate access keystroke sequence, a data depositoryconfigured to store the customization data, and means for generating theapplication user interface according to the customization data.

An embodiment of the present invention includes a method of developing acustomizable user interface element by selecting a customizableimmediate access keystroke sequence, developing a user interface elementassociated with the customizable immediate access keystroke sequence,determining a data record for holding a value used to characterize thecustomizable immediate access keystroke sequence, the data record beingstored in a data repository and being user modifiable, the datarepository being physically remote from a client used to display anapplication user interface, generating metadata defining thecustomizable immediate access keystroke sequence, the metadata includinga reference to the data record, and storing the metadata in associationwith the user interface element, the user interface element beingconfigured for inclusion in the application user interface.

An embodiment of the present invention includes a method of customizingan application user interface by accessing a page definition, the pagedefinition including metadata associated with a customizable immediateaccess keystroke sequence, using the metadata to access a data record,the data record being stored in a data repository and being usermodifiable, the data repository being physically remote from a clientused to display an application user interface, using information readfrom the data record to determine a value defining the customizableimmediate access keystroke sequence, generating markup-languageresponsive to the determined value, and including the generatedmarkup-language in the application user interface.

An embodiment of the present invention includes a customizableapplication system comprising an application server, an applicationinterface generator configured to generate an application userinterface, the application user interface including a customizable viewall command and configured as an interface between the applicationserver and a client, a web application server configured to deliver theapplication user interface to a client, means for specifyingcustomization data configured to characterize the view all command, adata depository configured to store the customization data, and meansfor generating the application user interface according to thecustomization data.

An embodiment of the present invention includes a method of developing acustomizable application user interface associated with an internetapplication by selecting a customizable view all command associated witha data record, the data record being stored in a data repository andbeing user modifiable, the data repository being physically remote froma client used to display the application user interface, including theview all command in the application user interface, generating metadataassociated with the view all command, the metadata including a referenceto the data record, and storing the metadata in association with theinternet application, the internet application being configured foraccess using the application user interface.

An embodiment of the present invention includes a method of customizingan application user interface by accessing a page definition, the pagedefinition including metadata associated with a customized property of aview all command, accessing the metadata to obtain a reference to a datarecord, using the reference to access the data record, the data recordbeing stored in a data repository and being user modifiable, the datarepository being physically remote from a client used to display anapplication user interface, reading information from the data record,using the information read to determine a value defining the customizedproperty, generating markup-language responsive to the determined value,and including the generated markup-language in the application userinterface.

An embodiment of the present invention includes an application systemcomprising an internet application system configured to support aninternet application, the internet application associated with metadataconfigured for generating an application user interface, the internetapplication system including both an application server configured togenerate the application user interface and a web application serverconfigured to deliver the application user interface to a client. Theembodiment further includes an application development system configuredto generated the metadata, the metadata being further configured tocharacterize a customizable find command included in the applicationuser interface a configuration system including a configuration engineand a configuration interface, the configuration interface configured tomodify configuration data characterizing the customizable find command,and a data repository including a data record for storing theconfiguration data, the data record being accessible using the metadata.In this embodiment the find command is optionally customizable to searchdata displayed in the application user interface. In this embodiment thefind command is also optionally customizable to search all rowsassociated with a result, a subset of all rows being displayed in theapplication user interface.

An embodiment of the present invention includes an application systemcomprising an internet application system configured to support aninternet application, the internet application associated with metadataconfigured for generating a plurality of application user interfaceseach having a customizable find command, the internet application systemincluding both an application server configured to generate at least oneof the plurality of application user interface and a web applicationserver configured to deliver the at least one of the plurality ofapplication user interfaces to a client, the find command beingcustomizable either to search all of a result or to search only a subsetof the result being displayed in the at least one of the applicationuser interfaces. The embodiment further includes a personalizationsystem with a personalization engine and a user profile interface, thepersonalization interface configured to modify personalization datacharacterizing the customizable find command such that the customizablefind command in more than one of the plurality of application userinterfaces is modified, a data repository including a data record forstoring the personalization data, the data record being accessible usingthe metadata.

An embodiment of the present invention includes a method of customizingan application user interface by accessing a page definition, the pagedefinition including metadata associated with a customized property of afind command, the customized property including the scope of a search,accessing the metadata to obtain a reference to a data record, using thereference to access the data record, the data record being stored in adata repository and being user modifiable, the data repository beingphysically remote from a client used to display an application userinterface, accessing the data record to determine a value defining thecustomized property, generating markup-language responsive to thedetermined value, and including the generated markup-language in theapplication user interface.

BRIEF DESCRIPTION OF THE VARIOUS VIEWS OF THE DRAWING

FIG. 1 illustrates an embodiment of a user interface configuration andpersonalization process representative of the present invention;

FIG. 2 illustrates elements of a customizable application system inaccordance with an embodiment of the present invention;

FIG. 3 illustrates an embodiment of an internet application system andassociated components of the invention;

FIG. 4 illustrates an embodiment of a DBMS server;

FIG. 5 illustrates an embodiment of a page development step thatincludes generation of metadata;

FIG. 6 illustrates an embodiment of an IDE;

FIG. 7 illustrates one example of a configuration step in which adeveloped user interface is customized to meets the needs of aparticular user or group of users;

FIG. 8 illustrates an embodiment of a configuration interface;

FIG. 9 illustrates details of a personalization step;

FIG. 10A illustrates an embodiment of a user profile interface;

FIG. 10B illustrates another embodiment of the user profile interface;

FIG. 11 illustrates examples of an initial presentation step and apresentation step;

FIG. 12 illustrates a tab-order interface used for specifying tab-order;

FIG. 13A illustrates an address entry form, such as may be found in anorder entry application component;

FIG. 13B illustrates the focus of a user interface located on a calendarbutton;

FIG. 13C is an expanded view of a portion of FIG. 13B.

FIG. 13D illustrates the focus of a user interface located on a statusdrop down list;

FIG. 13E illustrates an embodiment of a user profile interface includingtwo options relating to tab-over;

FIG. 14A illustrates an embodiment of an application user interfaceincluding a table showing the results of a query;

FIG. 14B illustrates an interface that is included in variousembodiments of the IDE;

FIG. 14C illustrates the result of executing a view all command;

FIG. 15 illustrates an interaction model wherein data entered by a useris immediately transferred to the internet application system;

FIG. 16 illustrates an interaction model wherein communication betweenan application user interface and an internet application system isdelayed;

FIG. 17A illustrates an embodiment of a configuration interface arrangedto allow customization of the interaction model used by an applicationcomponent; and

FIG. 17B illustrates an example of an option that allows a user tochange the interaction model while the internet application is running.

DISCLOSURE OF THE INVENTION

A new approach to designing, implementing and using user interfaces isdisclosed. This approach overcomes restrictions imposed by prior arttechnology and philosophy and includes new design methods that permitimplementation of user interfaces more appropriate for use as interfacesbetween consistent users and application programs. In particular, userinterfaces developed using these methods are no longer constrained bythe basic point and click interaction model. The new approach includes aunique system architecture, useable by user interface developers toprovide advanced customization and user control within an HTMLenvironment. The provided features include user modification of pageelement functionality and are thus important to the development,deployment and use of enterprise solutions as internet applications.

The unique system architecture of the present invention allows internetapplication developers to include customizable user interface elementsin application user interfaces. The customizable properties of theseelements include, but are not limited to, alternative functionality,arrangement and visibility. Customization of user interface elementsincludes both “configuration” that is applicable to multiple users and“personalization” that is applicable to an individual user.Personalization is a special case of configuration wherein informationis modified by or for individual users and saved in an individual userprofile. Configuration information is modified by a privileged user,such as a supervisor, and saved in a database associated with aninternet application. Both the user profile and configurationinformation are stored at a location physically remote from client-sideaccess systems, such as client web browsers. These aspects of the systemarchitecture avoid substantial client side processing or storage andthereby eliminate dependence on client-side environments. The advantagesinherent in this system architecture are achievable through an HTMLbased browser interface.

The new approach to user interface and web page design and interactionsatisfies needs of consistent users through a browser compatibleinterface. These needs include giving users the ability to customize thefunctionality of user interface elements associated with underlyinginternet application programs. For example, using the present inventiona user is able to control methods of data input and output, thepresentation of requested information, logical operations, orcharacteristics of communication between the browser compatibleinterface and servers. Configuration and personalization can be appliedto individual user interface elements, individual user interfaces andassociated web pages, all internet application user interfaces accessedby a user, or groups of user interfaces within a specific internetapplication. Control of functionality is particularly important inapplications designed as enterprise solutions. These types ofapplications are often used by consistent users who benefitsignificantly from interfaces evolved beyond the basic point and clickinteraction model.

Interaction between a user and an application includes input the usersupplies to the application and output presented to the user by theapplication. For example, a user may select user interface elements witha pointing device (e.g., a mouse), enter data in a field using akeyboard or voice recognition software, or use keystrokes to control anapplication. Configurable properties of user interaction includedefining the function of “hotkeys” and automatically placing a cursor ina preferred data entry field. Providing customization of this typeallows a user to choose between the basic point-and-click interactionmodel and a keyboard based interaction model. Under many circumstancesthe keyboard based interaction model enabled by the present invention ismore efficient and preferred.

The presentation of application output is customized with regard to thestyle of presentation, the amount of data presented on a single page,the order in which the data is shown, and the aspects of the data madevisible, among others. For example, in some circumstances it ispreferable to display just enough data to fill the viewing areaavailable to a browser. In other circumstances it is preferable todisplay data in a style suitable for users with diminished eyesight.

A functional property of a user interface element can include logic,data processing, and responsiveness to user input. For example, checkingthat data entered in a form field has an acceptable format is afunctional property of the form field element. This type of syntacticprocessing is typically performed by scripts included within the userinterface. Likewise, responsiveness to a hotkey can be a functionalproperty of a menu item. The functionality of user interface elementsalso includes the underlying processes associated with each element. Forexample, in an application interface, the underlying processes caninclude “business logic” typically executed on a server and designed toassure the validity of entered data. Business logic routines applybusiness rules such as range checking. This type of business logic may,for instance, be used to check that a start date is on or before afinish date. Other examples of user interface element functionalityinclude displaying error messages, modifying the order of element focus,and controlling when data is passed from a client to business logicprocesses performed on a server. Providing customization of functionalproperties of user interface elements is an advantage derived fromembodiments of the present invention.

FIG. 1 illustrates an embodiment of a user interface configuration andpersonalization process representative of the present invention. Themethod begins with an element development step 50. In this step one ormore individual user interface elements are designed or selected from alibrary of predefined user interface elements. These elements areconfigured for inclusion in an application user interface. In step 50,each element is optionally associated with an underlying internetapplication. For example, in one embodiment a predefined data entryfield is selected and associated with a procedure of the internetapplication configured to receive data entered in the field. In anotherexample, a menu item on a user interface is associated with anunderlying procedure that performs the process referred to by the menuitem.

The user interface elements developed in step 50 are optionallyspecified as having customizable properties. These properties are eitherattributes of a predefined user interface element or are selected duringthe design of the element by the user interface developer. For example,in one embodiment the specification process is simplified by accessing alibrary of user interface elements including properties that arecustomizable by default. In another embodiment a user interface element,including at least one configurable property, is designed from basicelements or a preexisting template. Step 50 optionally includesdetermination of a data record used to hold a value characterizing acustomizable property of the user interface element and generation ofmetadata including a reference to the data record. Default values aretypically stored in the data record.

In a page development step 100 an application user interface,incorporating a user interface element developed in step 50, isdesigned. The design process includes positioning of user interfaceelements, with configurable features and definition of default valuesfor these features and their configurable aspects, with respect to theapplication user interface. Step 100 is typically performed by adeveloper involved in the creation and/or publication of the applicationuser interface. The developer can include programmers, designers,graphic artists, publishers, and other parties involve in producing theapplication user interface and associated web pages. For example, in oneembodiment a programmer designates initial user interface elements andlayout, while a specialist familiar with a specific application setsdefault values. The information collected and generated in step 100 isstored in the form of metadata such as PeopleCode®, page definitions,and other data formats. This information includes data records andmetadata prepared in step 50 and defines the application user interface.The storage is in a location separate from the browser compatible system(client) of a user.

PeopleCode, developed by PeopleSoft, Inc., is a well-known programspecification language used in the development of enterpriseapplications. It may, for example be used to implement business logicrelated to the internet application. The metadata approach enhances themaintenance of internet applications, simplifies upgrade processes and,as described herein, enables multiple layers of customization in aninternet environment. In addition, the use of metadata also enhancesportability, by enabling support of various database systems, serverenvironments, and browsers.

In an optional configuration step 110, customization of the applicationuser interface developed in step 100 is performed by a privileged user,such as a system administrator, application specialist, or the like.This customization is the basis for a hierarchical set of configurationand personalization layers each typically having a narrower scope andtaking priority over more general layers. For example, in one instance asupervisor selects which application user interfaces are available tosales personnel and a member of the sales team specifies how a specificapplication user interface should function when the member accesses it.In this example, personalization specified by the member of the salesteam takes priority over configuration specified by the supervisor. Theconfiguration data provided by the supervisor in step 110 is stored forretrieval during application user interface generation. In alternativeembodiments customization is responsive to the identity of a clientrather than the identity of a user. Thus, users accessing the internetapplication from a client located in the sales department are presentedwith a user interface customized for that department.

Each configuration and personalization layer may apply to a differentscope within an internet application. For example, in one embodiment aconfiguration specification applies to a specific application component.An application component is a collection of user interface elements,associated application code, and other aspects of an internetapplication that perform a specific task or set of related tasks as partof an internet application. For instance, an application component mayinclude a set of user interface elements and underlying application codeused to accept a sales order or, alternatively, to generate a salesreport. An application component optionally includes one or moreapplication user interfaces that further include personalized userinterface elements. These application user interfaces are part of aninternet application including the application component and are used tocommunicate with a user. In other examples, customization applies to anentire internet application, users or clients who are members of agroup, groups of application user interfaces, and the like.

In an optional initial presentation step 120, the application userinterface developed in step 100 is presented to a user through a browsercompatible interface such as a web browser. The application userinterface is typically served as part of a web page over a computernetwork such as the Internet or an intranet. Since in preferredembodiments the system architecture relies only on the featuresavailable in a standard web browser, the presentation does not depend onadditional client side resources such as direct access to significantstorage or processing of additional client side computer code. Theapplication user interface is presented through any web browsercompatible system and the browser compatible system does not requireadd-ons, plug-ins, or extensions to support additional features.

In a personalization step 130 the user optionally customizes elements ofthe application user interface presented in step 110. The user accessesa personalization utility associated with their user profile. Thepersonalization utility is typically but not necessarily integrated aspart of the internet application. This utility is used by the user toselect and modify one or more personalization options available to theuser. In a save step 140, any modifications made in step 130 are savedas personalization data associated with the application user interfaceand the user's profile. The personalization data is preferably saved ata location separate from the browser compatible system of the user andis accessed using a user-associated key such as a user ID and/orpassword.

In a presentation step 150 the application user interface is againpresented to the user through a browser compatible interface. Duringpresentation step 150 the configuration data developed in step 110 andthe personalization data saved in step 140 is used to modify thepresented application user interface. The modification is performed by auser interface generation engine that accesses the saved configurationand personalization data and default page information defined in step100. The output of the page generation engine is markup-language data,such as HTML data, suitable for presentation as a web page, JavaScript®,and the like, that is presented through a browser compatible interfacewithout requiring browser add-ons or plug-ins. The output of the pagegeneration engine is differentiated from Java® code, ActiveX®, and otheradd-ons, plug-ins, or tools used to extend browser functionality, inthat the output is downloaded to a client as an integral part of anassociated user interface and thus does not reside on the clientindependently from the associated user interface.

A detailed description of the unique system architecture, used tosupport the method illustrated by FIG. 1, is presented herein. Thisdiscussion includes several illustrative examples in which the systemarchitecture is used to configure and personalize functional propertiesof user interface elements associated with an application. In oneexample, a user modifies means of user input and ways in which theapplication responds to this input. In another example, a user selectshow requested data is presented to a user. In yet another example, auser selects between interaction models used for communication betweenthe browser interface and server-side components of an application.These examples are meant to be illustrative. The systems and methodsdisclosed are optionally used to provide user customization of anyfunctional or nonfunctional property of a user interface.

In the preferred embodiment of the present invention, the unique systemarchitecture uses a standard web browser as a client and does notrequire additional client-side application software. Internetapplication programs supported by the invention can use a standard webbrowser for user interaction because the user interface (web page)generated by the present invention is based on HTML and JavaScript thatis independent of proprietary browser extensions such as vendor-specificDynamic HTML, Java Code based user interface extensions, or otherclient-side controls and code. The generated interface also takesadvantage of the capabilities of browsers and the internet, such ashyperlinks, and is thus not merely an emulation of a Microsoft Windows®interface.

The internet application user interface is generated at a server,delivered to the client web browser in HTML/JavaScript form, andrendered for the user at the client device. Nothing is required of theclient other than the ability to support standard browser protocols suchas HTTP and HTML. No additional executables are required on the client.

The system supporting the browser client does not have to be atraditional web browser, such as Microsoft Internet Explorer® orNetscape Navigator®, running on a personal computer. The client isalternatively a handheld wireless device such as a cellular phone orsome other browser compatible device. Wireless applications use anarchitecture, known as Wireless Access Protocol (WAP), that is similarto that used by traditional internet-based applications accessed througha web browser running on a personal computer. The WAP applicationstandard is based on internet standards, such as Extensible MarkupLanguage (XML), HyperText Transfer Protocol (HTTP) and Secure SocketsLayer (SSL). The architecture of the present invention is well suited tothe characteristics of limited functionality (e.g., available memory andprocessing power) systems including many wireless and non-wirelessdevices.

FIG. 2 illustrates elements of a customizable application system,generally designated 200, in accordance with an embodiment of thepresent invention. These system elements include an applicationdevelopment system 210, an application execution system 215, and atleast one or both of an optional personalization system 220 and anoptional configuration system 225.

Application development system 210 is used by application developers todevelop user interface elements in step 50 (FIG. 1) and to layout theseelements in a user interface in step 100. In one embodiment the userinterface is integrated into the internet application associated withthe user interface elements. Steps 50 and 100 of FIG. 1 are preferablyaccomplished using an application designer 230 accessed through anintegrated development environment (IDE) 235.

IDE is optionally used for user interface development without requiringthat a user interface developer directly write HTML or JavaScript. Asshown herein, HTML and JavaScript are subsequently generatedautomatically. IDE 235 has many features and commands in common withgraphical software development systems such as Visual Basic® as well asHTML page design tools found in systems such as Microsoft FrontPage®.Thus IDE 235 is both a program development tool and a design tool fordesigning browser compatible user interfaces (web pages). For example,in one embodiment IDE 235 is used to develop a user interface element,associate the user interface element with an internet application,position the element on a user interface, and designate the generationof PeopleCode for checking the validity of data entered using the userinterface element. IDE 235 is used to perform steps 50 and 100 asillustrated in FIG. 1.

Application designer 230, is responsive to user input received by IDE235 and generates metadata defining a user interface, customizableelements within the user interface, and the association between elementsof the user interface and processes and application data of anunderlying application. Metadata is definitional data that providesinformation about or documentation of other data managed within a dataprocessing application. Metadata is used, for example, to define objectdefinitions within the system, such as business processes, components,fields, file layouts, indexes, menus, messages, pages, PeopleCodeprograms, queries, and other records. This metadata is stored in a datarepository 240 typically including a database management server (DBMS)245. Metadata is modified using application development system 210.

Application execution system 215 includes an internet application system250 arranged to support an application program and manage an associatedHTML/JavaScript based application user interface 255. Internetapplication system 250 receives data generated using IDE 235 and storesit in Data Repository 240. During internet application executioninternet application system 250 retrieves data from data repository 240and uses the retrieved data to generate a customized application userinterface 255 displayed to a user in one or more web pages. Applicationuser interface 255 is an HTML based interface typically generated inresponse to a user request. The retrieved data optionally includesinformation that has been modified by a user as part of a customization.Application execution system 215 is used during initial presentationstep 120 and presentation step 150 of FIG. 1.

Personalization system 220 is accessed through a user profile interface270 and includes a personalization engine 265 configured for a user tomodify information stored in data repository 240. As with other elementsof the invention, personalization engine 265 and user profile interface270 are optionally integrated directly into internet applicationssupported by and accessed through the invention. Personalization system220 is used during personalization step 130 of FIG. 1.

Configuration system 225 includes a configuration engine 260 and aconfiguration interface 275. Configuration system 225 is typicallyarranged to modify an entire application, a part thereof, or thepreferences of more than one user. Use of configuration system 225generally requires greater access permissions than personalizationsystem 220. Configuration system 225 is typically used to set group,department (sales, accounting, etc.) or enterprise wide preferences inconfiguration step 110 of FIG. 1.

FIG. 3 illustrates an embodiment of internet application system 250 andassociated components of the invention. Internet application system 250typically includes a web application server 305 configured as aninterface to outside systems and an application server 309 configured tosupport the execution of internet applications and generate applicationuser interface 255 (FIG. 2). One embodiment of web application server305 includes subsystems well known in the art such as presentation relayservlet 306, integration relay servlet 307, and portal servlet 308.

Web application server 305 communicates, using standard protocols, withoutside systems such as a web browser 310 within programmable device323, a wireless system 315, and an external system 325. Thiscommunication is typically through a computer network 322, such as alocal network, a wireless network, a wide area network, the internet, orthe World Wide Web. Web browser 310 executes on a programmable device323 such as a workstation, personal computer, personal digitalassistant, or the like. Alternatively, web application server 305communicates with a wireless system 315 using HTTP and WAP. Webapplication server 305 optionally includes utilities, such as WebSphere®(International Business Machines, Armonk, N.Y.), and WebLogic® (BEASystems, Inc., San Jose, Calif.), that are well known in the art. Theseutilities serve to perform the functions expected of a web server and asinterfaces between web application server 305 and components ofapplication server 309.

Application server 309 is configured to support and execute the internetapplication program. These tasks include the generation ofHTML/JavaScript based application interface 255. In one embodimentinternet application system 250 uses an application engine 330 toexecute application logic. Application engine 330 is a batch processingprogram optionally used to execute business logic developed by anapplication designer. Query processor 335 is used to execute queriesthat are generated by a system user. In some embodiments aspects ofapplication server 309 are configured to make use of external code suchas program modules written in C++ or the like. Application messagingprocessor 343 is used to send and receive messages between applicationsfor application to application integration. User interface generator 340produces customized application user interface 255 (FIG. 2). Interfacegenerator 340 and query processor 335 are supported by SQL accessmanager 348. In support of interface generator 340, SQL access manageris used to form queries for the retrieval of data, such as configurationdata, from data repository 240 (FIG. 2). These queries are applied todatabases, such as DBMS server 245 (FIG. 2).

Application server 309 further includes a business interlink processor350 configured to facilitate communication with and execution of thirdparty applications that are optionally used to add functionality to theinternet application as is well known in the art. A component processor355 is configured to execute aspects of the internet application.Application server 309 also includes server utilities well known in theart, such as a Tuxedo® interface system 360 from BEA Systems (San Jose,Calif.) which is used in the execution of business logic. Applicationserver 309 contains other elements well known in the art such as anoptional portal processor 365 that is used to handle the processing ofdata requests and instructions passed to and from user-applicationinterface 255 (FIG. 2) when user-application interface 255 works insidea portal, a security manager 370, a directory server 375, and a processscheduler 380.

DBMS server 245, within data repository 240, stores personalization dataassociated with each user profile and configuration data associated witheach internet application supported by the present invention.Information associated with the internet application and each user isheld in DBMS server 245 or elsewhere within data repository 240. Thisinformation can include, for example, application data tables, metadata,configuration data, and the like.

FIG. 4 illustrates an embodiment of DBMS server 245 (FIG. 2). DBMSserver 245 includes system data, metadata such as PeopleCode 420 andapplication component data 430, configuration data 440, and user datasuch as a user profile 450. Application component data 430 includesinformation associated with specific application components, such as therelationships between user interfaces and underlying application code,application data, application processes, PeopleCode, and the like. DBMSserver 245 is optionally located on one or more computing devicesphysically separate from internet application system 250 (FIG. 2).

One embodiment of an application component is arranged for order entry.This application component is associated with application component data430 specifying properties of user interfaces arranged to allow users toenter buyer and product information relating to an order. These userinterfaces are included in several embodiments of application userinterface 255 (FIG. 2) and are configured for entering accountinformation, items being ordered, and such.

Application component data 430 optionally includes aspects ofconfiguration data 440, and aspects of supporting PeopleCode 420 (FIG.3), and is typically developed using application development system 210(FIG. 2). Configuration and personalization at the application componentlevel is advantageous because user interaction with an internetapplication is often characterized by performance of a specific task orset of related tasks. Configuration data 440 is therefore optionallyincluded as an aspect of application component data 430.

Configuration data 440 includes information used to customize a userinterface before the user interface is included in an embodiment ofapplication user interface 255. Configuration data 440 optionally ispopulated with default values using application development system 210during page development step 100 (FIG. 1) and is also modified usingconfiguration system 255 during configuration step 110. In alternativeembodiments configuration data 440 is specific to the internetapplication, groups of users, individual user interfaces, geographiclocations, or the like. In these embodiments configuration data is alsooptionally stored in association with specific application components orother aspects of an internet application.

Personalization data 473 is configuration data 440 that is specific toan individual user and is optionally found in association with a userprofile 450. In alternative embodiments user profile is associated witha specific user, a class of users, a specific client or a class ofclients. In addition to personalization data 473, user profile 450includes user information 470 which is composed of data such as a user'sname, a user ID, user privileges, and the like. Personalization data 473includes element personalization data 476, page personalization data479, component personalization data 482 and internet applicationpersonalization data 485. These data are used for personalization at theelement, component, individual application web page, and internetapplication levels respectively.

Metadata stored in DBMS server 245 are used by processes on applicationserver 309 to generate the application user interface 255. Thesemetadata are used to define HTML and JavaScript data included in anembodiment of application user interface 255. Specifically thesemetadata include data defining specific user interface elements, such asdata records containing specific fields used to store properties of theuser interface elements. The metadata also include menu definitions,page definitions, PeopleCode, business process definitions, and thelike. The use of metadata in the user interface generation process is aproperty of the present invention that simplifies the incorporation ofcustomized information in the resulting user interface. Metadataincludes references, such as queries or pointers, to data recordsholding user defined data customized using configuration system 225and/or personalization system 220. As shown herein, metadata is used byprocesses on application server 309 to retrieve appropriateconfiguration and personalization data at the time of user interfacegeneration.

In an alternative embodiment of data repository 240 (FIG. 2) themetadata further includes information defining the type of data that canbe found in a specific data record. This feature allows an individualdata record within DBMS server 245 to hold data of variable type. Forexample, a record may hold a specific value, or alternatively, an SQLquery configured to retrieve a specific value from another part of DBMSserver 245 or another location. In this embodiment user interfacegenerator 340 (FIG. 3) uses information associated with the metadata todetermine the type of data stored in the data record and process itaccordingly.

In various embodiments of the present invention, metadata is edited orgenerated as a result of a developer using application developmentsystem 210 (FIG. 2). For example, during page element development step50 (FIG. 1) a developer defines or selects a user interface element andassociates it with a procedure (function) of an internet application.This results in the definition of metadata fields used to storeproperties of the user interface element. These fields are included indata records stored in data repository 240. In one embodiment thedeveloper specifies specific aspects of the user interface element to becustomizable. During Page Development step 100 the user interfaceelement is included in a specific application user interface 255. As aresult, metadata is generated indicating properties such as the relativelocation of the user interface element in the specific application userinterface 255. If a property of the user interface element iscustomizable, the metadata is used by the SQL access manager 348 togenerate means, such as an SQL query, for accessing values storedelsewhere, such as configuration data 440 or personalization data 473.In practice, these values stored elsewhere are adjustable usingconfiguration system 225 and/or personalization system 220 (FIG. 2).

Using metadata to define properties of a user interface element, anentire application user interface 255 or an application component, andusing the metadata in combination with the customization data togenerate application user interface 255 when needed, allows anyproperty, both functional and static, of a user interface element to becustomizable. In addition, since configuration data 440 andpersonalization data 473 are optionally separate from other aspects ofan internet application, various users can be subject to various sets ofconfiguration (and personalization) data. Therefore, two users can seedifferent customized versions of the same application component, aspresented through application user interface 255. This can occur evenwhile both users are accessing the component at the same time.

FIG. 5 illustrates an embodiment of page development step 100 (FIG. 1)that includes generation of metadata. As discussed with reference toFIG. 1, in step 100 a developer uses IDE 235 (FIG. 2) to add or modifyuser interface elements on an application user interface 255. Inaddition to selecting and positioning user interface elements, adeveloper can optionally specify default values for a user interfaceelement. The process begins in an access IDE step 510 wherein adeveloper accesses application designer 230 using IDE 235. In an openpage step 520 a new or existing application user interface 255 is openedin IDE 235. In some embodiments step 520 includes opening a group ofapplication user interfaces 255, related to an application component, tobe developed as a single unit. In a locate element step 530 a userinterface element is selected and located (positioned) on the userinterface opened in step 520. The user interface element may includetext, graphics, images, fields, buttons, and the like.

In a select customizable properties step 540 a property of the selecteduser interface element is selected by the developer using IDE 235. Thisproperty is a customizable property of the user interface element bydefault if the user interface element was selected in step 50 (FIG. 1)from a library of previously defined customizable elements.Alternatively, if the user interface element was developed by adeveloper in step 50, then the property is customizable because it wasspecifically specified as being customizable by the developer. Thisspecification is used to generate metadata that enables administratorsor other users to later change (customize) the property of the selecteduser interface element.

In an optional select permissions step 550 permissions for performingconfiguration or personalization of the property selected in step 540are determined. The ability to customize a property is optionallydependant on security aspects such as a password and/or the identity ofa user or client. The permissions set in step 550 are default valuesthat may later be changed by a supervisor or other privileged user. Inan optional set defaults step 560 further default values associated withthe configurable property are determined. For example, if theconfigurable property is a number of columns to show in a table, then anactual value for the number of columns is set in step 560. Inalternative embodiments step 560 is performed as part of a separateprocess, for example during installation of the internet application.

Page development step 100 (FIG. 1) is concluded with a save pagedefinition step 570 that makes the developed application user interface255 (FIG. 2) and associated internet application functionalityaccessible to users. In this step metadata associated with theapplication including customizable and static aspects of applicationuser interface 255 are generated and saved in metadata and optionallynon-metadata formats. Information saved can include the application userinterface 255, PeopleCode 420, application component data 430, and thelike. Metadata optionally includes segments of HTML and JavaScript aswell as information about attributes of specific data records. Theseattributes optionally include the data format of the data record,information about a configurable property or a reference tocustomization data such as page personalization data 479. In analternative embodiment a data record includes metadata indicative of thedata format found in a specific metadata field. For example, in oneinstance a data record includes information indicating that the nextdata field contains a URL. Characteristics of the metadata indicate to aprocess accessing the metadata record that the next data field is to betreated accordingly. Data saved in step 570 is saved in a location, suchas data repository 240, that is accessible to internet applicationsystem 250.

FIG. 6 illustrates an embodiment of IDE 235 (FIG. 2) as used in pagedevelopment step 100 (FIG. 1). The embodiment shown includes a new pagebutton 610 and a user interface being developed 620. The user interfacebeing developed 620 includes data entry fields 640, check boxes 650, andtext elements 660. While the ability to position user interfaceselements such as these on a user interface is found in standard webdevelopment environments, IDE 235 includes features specific to thepresent invention. Following save page definition step 570 (FIG. 5),user interface being developed 620 may be presented to a user as aninstance of application user interface 255.

FIG. 7 illustrates an example of configuration step 110 (FIG. 1) inwhich an application user interface 255 (FIG. 2) developed in step 100is customized to meets the needs of a particular user or group of users.Configuration step 110 is initiated when an administrator, supervisor,or similarly privileged user connects to internet application system 250(FIG. 2) in a connect step 710. This connection provides the privilegeduser access to configuration system 225. Permission to use configurationsystem 225 is optionally responsive to a security step 720 wherein theprivileged user must pass a security protocol that establishes theiridentity and/or authorization and results in appropriate accessprivileges. In step 720 security manager 370 (FIG. 3) accesses optionaldirectory server 375. Directory server 375 includes data such asusernames, passwords, privileges, and the like, that are used toauthenticate users or clients and determine the privileges held by each.In alternative embodiments this information is saved in data repository240 instead of directory server 375.

In an access configuration data step 730 the privileged user usesconfiguration system 225 to access configuration data 440 (FIG. 4)associated with an internet application. The ability to access andmodify configuration data 440 is dependant on the specified privilegesof a user. For example, in one embodiment a supervisor responsible foraccounting department processes is only able to access applicationcomponents related to this department.

In a select property step 740 the privileged user selects a property ofthe user interface element to customize. The selected property is afunctional or static property that was made configurable during pagedevelopment step 100 or element development step 50. The selectedproperty is also, in various embodiments, specific to an entire internetapplication or to a part of an internet application such as anindividual user interface element, a specific application user interface255, an application component, or the like. For example, in oneembodiment the selected property is static text to be displayed on abutton whenever that button is used in an internet application. Inanother embodiment the selected property is specific to an applicationcomponent and is a functional “immediate access” keystroke combinationthat will cause a cursor to move to a specific field.

In an optional display options step 750 the privileged user views one ormore options available for the property selected in step 740. Theseoptions are typically determined during page development step 100 orelement development step 50. For example, in one embodiment a developerspecifies ten possible columns that can be included in a table. In thisembodiment of step 750 descriptions of the ten possible columns aredisplayed to the privileged user as a list. By specifying limitedconfiguration options, the developer can assure that configuration isrestricted to reasonable choices.

In an enter data step 760 the privileged user selects one of the optionsdisplayed in step 750 or alternatively enters other data relating to theproperty selected in step 740. For example, in one embodiment theprivileged user selects four of the ten possible columns displayed instep 750 to be included in a table. In an alternative embodiment, theprivileged user enters a keystroke combination to be used for immediateaccess. The selection made in step 760 is reflected in a customizedapplication user interface 255.

In an optional select scope step 770 the privileged user determines thescope of the selections made in steps 740 through 760. For example, inone embodiment the configuration is applied to only one user interfaceelement on a specific user interface for a specific user. In analternative embodiment the configuration is applied to all of aninternet application (or applications) irrespective of user or clientidentity. In other embodiments scope is specified with respect toapplication components, individual user interfaces, particular groups ofusers, classes of user interface elements (field, button, image, etc.),and the like.

In a save configuration data step 780 the information generated in steps740 through 770 is saved to DBMS server 245. As described furtherherein, this information is used in the generation of customized userinterfaces, such as a customized application user interface 255.

FIG. 8 illustrates an embodiment of configuration interface 275 (FIG. 2)used by a privileged user to perform configuration step 110 (FIG. 1).The configuration options available in configuration interface 275 aredetermined by selections, such as specification of configurableproperties of a user interface element, made in page development step100. In this embodiment, configuration interface 275 includes rowsassociated with customizable properties such as an “expert entry”property 810 and various “tab” properties 820 as further describedherein. Each property is further associated with an “enable option”checkbox 840 and an “allow user value” checkbox 850. The state of theenable option checkbox 840 determines whether an option is used.Similarly, the state of the allow user value checkbox 850 determineswhether a user can enter their own (personalized) values for the option.Each property listed in configuration interface 275 is also associatedwith a default value 860. Magnifying glass buttons 830 are used todisplay lists of allowed values as explained in display options step 750(FIG. 7).

FIG. 9 illustrates details of personalization step 130 (FIG. 1) in whichaspects of an internet application are personalized. In contrast withconfiguration, personalization is performed using personalization system220 (FIG. 2) at the level of a single user and, therefore, typicallyaffects only that user. Except for factors relating to these changes incustomization level, steps 910 through 980 of FIG. 9 are similar tosteps 710 through 780 of FIG. 7. For example, an optional security step920 differs from security step 720 in that the permission required toaccess personalization settings of a single user is generally less thanthe permission required to modify the customization settings of multipleusers. In a typical implementation each user has default permission tomodify their own personalization settings.

In another example of difference between the steps of FIG. 7 and FIG. 9,access personal profile step 930 typically includes accessing thepersonal profile 450 (FIG. 4) of a user rather than configuration data440. In one embodiment the properties available for modification in aselect property step 940 and the options displayed in a display optionsstep 950 are limited by the permissions held by the user. The data thata specific user is permitted to enter in an enter data step 960 may besimilarly limited. In a select scope step 970 the allowed scope istypically limited to the current user and a save personalization datastep 980 is optionally part of save step 140 (FIG. 1).

FIGS. 10A and 10B illustrate two embodiments of user profile interface270 (FIG. 2) that are used to perform personalization step 130 (FIG. 1).User profile interface is typically an embodiment of application userinterface 255. The embodiment of user profile interface 270 illustratedin FIG. 10A includes facilities for changing general aspects, such as ane-mail address 1005 associated with a user. This embodiment alsoincludes facilities for changing an alternate user property 1010 byproviding an alternate user ID 1020. The embodiment of user profileinterface 270 illustrated in FIG. 10B includes a table of customizableproperties 1030, their default values 1040, and a field 1050 forentering personalized values.

FIG. 11 illustrates examples of initial presentation step 120 andpresentation step 150 of FIG. 1. These steps both include generation ofa customized user interface yet differ with respect to the availabilityof user modified personalization data 473 (FIG. 4). User modifiedpersonalization data 473 is available only after personalization step130 and is therefore not always available during initial presentationstep 120. Instances of customized application user interface 255generated in steps 120 and 150 are delivered to a client for display toa user. The present invention anticipates that the steps illustrated byFIG. 11 are alternatively executed in a variety of sequences.

In an identify requestor step 1110 a user initiates communication withinternet execution system 215. Identification is optionally made withrespect to a specific user, class of users, specific client or class ofclients. The requester may be a specific external client, a human useror, in some embodiments, an external process. In various implementationsidentity is established through a user ID provided from the client, byaccessing a standard browser cookie (or similar data) on the client, byvirtue of an established secure session, or by a similar approach as iswell known in the art. The identity established in step 1110 is used byother processes whose function is user or client dependent.

For example, the identification made in step 1110 is optionally used toperform a query user profile step 1115. In step 1115 informationrelating to the requester is retrieved from user profile 450. Onceretrieved this information is typically available for personalization ofapplication user interface 255 until the current session between therequestor and application execution system 215 is completed. Inalternative embodiments query user profile step 1115 is performed aspart of subsequent query operations, such as steps 1125 and 1145discussed herein.

In a select component step 1120 the requester selects one or moreapplication components available through the current internetapplication. In some embodiments step 1120 is optional. For example,when only one application component is available or if all applicationcomponents are to be made available. In some embodiments step 1120 isperformed using a menu of application components.

Select component step 1120 may include an optional query component datastep 1125. In step 1125 application component data 430 and/orconfiguration data is retrieved from data repository 240. Data retrievedin step 1125 may include all the metadata associated with eachapplication user interface 255 associated with the application, metadataassociated with components selected in step 1120, only page definitionsrelating to selected instances of application user interface 255, orsome variation thereof. In alternative embodiments this data iscollected during other query operations, such as step 1115 or step 1145.

In a receive page request step 1130 application execution system 215receives a request for an instance of application user interface 255from an external client such as web browser 310, wireless system 315, orexternal system 325 of FIG. 3. This request optionally includes auniversal resource locator (URL) or similar locating information used toidentify the particular application user interface 255 being requested.In some embodiments step 1130 includes a request for application datacorresponding to values provided by the user. For example, step 1130optionally includes search terms, keys or commands entered by a user ina field and used to retrieve application data. The search terms may beused as database keys that initiate the execution of processes relatedto the application component or are used to retrieve application datacorresponding to the keys. Web application server 305 passes the pagerequest to application server 309 that in turn initiates processes tofulfill the request. Receive page request step 1130 is typicallyperformed each time the execution of the application component requiresa new instance of application user interface 255.

Another process initiated by application server 309 performs an accesspage definition step 1140. Step 1140 is optionally performed prior tostep 1130 and includes collection of information required to generate aninstance of application user interface 255. The collected informationincludes data developed during page development steps 100 and 50(FIG. 1) as well as data specifying customized properties such asconfiguration data 440 and personalization data 473. The collected dataincludes metadata defining characteristics of the instance ofapplication user interface 255 and/or characteristics of individual userinterface elements. The completion of step 1140 may be followed byexecution of query customization data step 1145 wherein personalizationdata 473 or configuration data 440 is queried. Query customization datastep 1145 is used to retrieve any additional data, such as configurationor personalization data, required to generate the application userinterface 255.

In a generate HTML step 1150 application server 309 uses the metadataand other information collected to generate HTML. User InterfaceGenerator 340 generates HTML by interpreting the metadata and using datacollected from data repository 240 as required. Generate HTML step 1150is concluded when references to required data are resolved and the datarequired to display a customized application user interface 255 isgenerated. This data optionally includes browser compatible formats suchas JavaScript, HTML, WAP, and the like. Resulting valid HTML constructsare serialized, optionally packaged as a web page, and delivered to theclient in deliver interface step 1160. Incorporation of personalizationdata 473 and/or configuration data 440 in the HTML results in aninstance of application user interface 255 personalized or configuredaccording to the wishes of a user. This instance optionally includesJavaScript or other data compatible with a standard (unmodified) webbrowser. Steps 1130 through 1160 are typically performed one or moretimes during the execution of an application component.

Metadata relating to specific user interface elements optionallyspecifies personalized or configured aspects of the requested page. Inthese cases relevant values from the customization data collected in theabove steps are used in generate HTML step 1150. For example, in oneembodiment a required user interface element is a button and userinterface generator 340 uses personalization data associated withtab-over to decide whether the button should be included in thetab-order. In another embodiment the use interface element includes runtime processing, such as when an application developer has specifiedthat an expert entry mode is allowed. In this case user interfacegenerator 340 uses personalization data specific to an individual userto generate responsive HTML and JavaScript.

In alternative embodiments the metadata includes or is used to constructa value or a reference, such as a pointer, URL, or a query, to anotherlocation. This may include a numerical value, such as a font size, oralternatively include more complicated data such as a segment ofJavaScript or an e-mail address. This may also refer to, and be used toaccess, data records within configuration data 440, personalization data473, directory server 375, or other aspects of Data Repository 240. Datarecords within configuration data 440 and personalization data 473include supervisor or user modified information that becomesincorporated in a customized application user interface 255 delivered tothe requester.

Access page definition step 1140, generate HTML step 1150 and the use ofmetadata are further illustrated by the following examples. In oneembodiment of step 1140 a requested user interface includes aconfigurable user interface element with a user customizable textproperty (e.g., string or format) used to label the configurable userinterface element. Application server 309 accesses a user interfacedefinition related to the requested application user interface 255 thatwas developed in page development step 100 (FIG. 1). The user interfacedefinition is retrieved during steps 1125 or 1145 and includes aspecification indicating where on application user interface 255 thecustomizable user interface element should be located. The userinterface definition also includes a reference to a data location wherethe text property of the configurable user interface element may befound.

A customized application user interface 255 optionally includes a numberof configurable user interface elements, each further including a numberof configurable properties. Data required to generate individual userinterface elements is optionally collected at different times, even whenthe user interface elements are included in the same instance ofapplication user interface 255. For example, in one embodiment thecustomizable order of columns in a table are determined when theapplication component using the table is selected in step 1120. In analternative embodiment the order is determined when the information isfirst required in an instance of step 1140. Data relating to userinterface elements responsive to the run time requirements of theapplication component, such as those including JavaScript, are typicallycollected in step 1145 shortly prior to generate HTML step 1150. TheHTML and/or JavaScript generated in step 1150 is delivered to a clientin deliver interface step 1160.

Once the HTML or JavaScript defining a user interface element isgenerated the generated data is optionally cached in a cache data step1170. When possible the cached data is retrieved when the user interfaceelement is next required. Retrieving a cached copy prevents unnecessaryrepetition of generate HTML step 1150. In addition, cache data step 1170may include storage of other static aspects of the generated applicationuser interface 255, such as page definitions, style sheets, images, andJavaScript.

The user interface generation process optionally operates independentlyfrom the type of data stored within DBMS Server 245 and the number ofquery operations required to generate a requested page. Thisindependence enables the inclusion of references to customization data,such as configuration data 440 and personalization data 473, andinclusion of this data in the generated application user interface 255,without modification of the user interface design developed in pagedevelopment step 100. The ability to include customized data withoutmodifying page design is thereby achieved in an HTML/JavaScriptinterface supported by a standard browser.

An alternative embodiment includes multiple and/or recursive executionof query steps 1115, 1125 or 1145. Through the use of multiple querysteps multiple levels of configuration and personalization are possible.For example, in one embodiment the result of a query step includesfurther metadata requiring a subsequent query to retrieve further data.

Steps 1125 and 1145 optionally use the requester identity determined instep 1110 to determine permissions and develop appropriate queries. Forexample, requester identity is used to determine which personalizationdata 473 to query and to resolve configuration data 440 whose scope isuser dependent. In many instances the requester identity is included asa parameter in a query.

Embodiments of the invention include configuration of user interfaceproperties that include keystroke functionality. This allows users orsupervisors to modify the response of user interface elements tokeystroke combinations. Examples of keystroke configuration includecustomization of “tab-order,” “tab-over,” “hotkey,” and “immediateaccess key” functionality.

Tab-order functionality determines the order in which the tab keychanges “focus” among user interface elements. With respect toapplication user interface 255, the “focus” is the user interfaceelement on which the cursor rests or to which action is directed. Fortext entry fields focus is usually indicated by the presence of a textcursor or highlighting of the text entry field. For buttons, othergraphical objects and links the focus is typically indicated by a dottedline highlighting the object. Tab-order is typically determined by thesequential order in which elements are placed on a user interface or bythe order of an original web page design. Customization of tab-orderincludes altering this default order. For example, in one embodiment thetab-order is changed to match the order in which data is preferablyadded to a form.

Tab-over is a particular case of tab-order that allows a user interfacedesigner, supervisor, or user to indicate that certain user interfaceelements should be skipped in the tab-order. For example, a user canpersonalize an application component such that the tab-order ignores allbuttons and graphic objects, stopping only at text entry fields wherethe user wishes to enter data. Alternatively, application user interface255 is optionally customized such that the tab-order only includes textentry fields and a “next” button that is used to request the nextrequired user interface.

A hotkey is a keystroke combination that results in the execution of anoperation. For example, the Ctrl-C keystroke combination is often usedto copy something to an electronic clipboard. Likewise, the Ctrl-Skeystroke combination is often used to execute a “save” command. Theinclusion of hotkeys in an internet application greatly increases theutility of the application. For example, including a Ctrl-N keystrokecombination to automatically request the next page in an applicationcomponent. In further examples, the Ctrl-K keystroke combination isoptionally customized to display a help screen containing informationrelating to the user interface element with the current focus and Ctrl-5is optionally customized to prompt a user for input. Hotkeys aregenerally used to save the user the trouble of using a pointing deviceto move a cursor to a graphical button, a potentially time-wastingaction for an experienced user. Because hotkeys can have differentmeanings in various environments and to different users it is helpfulfor a user to be able to customize the hotkeys associated with aninternet application. For example, the Ctrl-N keystroke sequence willcause the Microsoft Internet Explorer® browser, in its standardconfiguration, to reload the existing page. Thus, this sequence would bea poor choice for requesting the next page when using this browser.Since hotkeys are either not available or not standardized in browserenvironments it is an important aspect of portability to be able toconfigure these keystroke combinations such that conflicts found in thedifferent environments can be avoided.

Immediate access key functionality allows the focus on an applicationuser interface 255 (FIG. 2) to be directed to a specific user interfaceelement associated with an immediate access keystroke combination. Forexample, in one embodiment an immediate access keystroke combination isused to place a text cursor in a specific text entry field. The focus ischanged to this text entry field upon typing of the immediate accesskeystroke, regardless of the prior focus location. Hotkey keystrokesequences are a type of immediate access keystroke sequence.

FIG. 12 illustrates a tab-order interface 1200 used for specifyingtab-order, and found in various embodiments of IDE 235 and, optionally,configuration interface 275. Tab-order interface 1200 includes a row1210A-1210R for each user interface element on an associated applicationuser interface 255. The columns of tab-order interface 1200 include alabel 1220 identifying the user interface element and a user interfaceelement type 1230, such as “EDIT BOX” or “DROP DOWN LIST,” thatdescribes a class of the user interface element. The columns alsoinclude various user interface element control settings 1240, and a userinterface element level 1250. These entries are used to establishrelationships and interdependencies between user interface elements. Thetab-order is determined by the order of rows 1210, and optionally thelevel 1250 value or a control setting 1240. For example, in oneembodiment the user interface element associated with row 1210J will befollowed by the user interface element associated with row 1210K in thetab-order. Customization is accomplished by changing the order of therows 1210. A similar interface is used to customize other keystrokefunctionality.

The row 1210A-1210R order illustrated in FIG. 12 is used during savepage definition step 570 (FIG. 5) to generate metadata. This metadatareferences information about the tab order of various user interfaceelements, which in turn are used by components on application server 309to generate the appropriate HTML code. Specifically, the metadataoptionally includes either an appropriate value for a TABINDEX attributeof various user interface elements within the user interface, orincludes JavaScript that “traps” the tab key when the focus is on thelast object to which the user wishes to tab. This JavaScript is used tomove the focus from the last object back to the first object. TABINDEXis an HTML parameter introduced in recent HTML standards and used tospecify tab-order. The configuration of other aspects of keystrokefunctionality makes similar use of JavaScript or HTML keywords.

FIGS. 13A through 13E illustrate customization of keystrokefunctionality in an embodiment of application user interface 255. FIG.13A illustrates an address entry form, such as may be found in an orderentry or customer management application component. The address entryform includes a date field 1310, a calendar button 1320, a “Status” dropdown list 1330, a submit check box 1335, a description field 1340 and an“Address” field 1350 among others. In FIG. 13A the focus is on datefield 1310 as indicated by the highlighting. By default, pressing thetab key moves the focus to calendar button 1320, as illustrated in FIG.13B. FIG. 13C is an expanded view of a portion of FIG. 13B showingdetail of a dotted line 1360 that indicates the presence of the focus oncalendar button 1320. Pressing the tab key again moves the focus tostatus drop down list 1330, as shown in FIG. 13D. In one instance oftab-order configuration, the tab-order is changed such that the firstpressing of the tab key moves the focus from the date field 1310 (asshown in FIG. 13A) to the status drop down list 1330 (as shown in FIG.13D) and the second pressing of the tab key moves the focus from thestatus drop down list 1330 to description field 1340.

In one embodiment of tab-over customization, all button objects, such ascalendar button 1320, are skipped in the tab-order. In this instancepressing the tab key for the first time moves the focus from the datefield 1310, as shown in FIG. 13A, directly to status drop down list1330, as illustrated in FIG. 13C. Using tab-over customization to skipcalendar button 1320 in the tab-order reduces the number of keystrokesrequired for a consistent user to enter data in the address entry form.As with other tab-order customization, an individual user can typicallyturn on and off a button object skipping feature. FIG. 13E illustratesan embodiment of user profile interface 270 that includes two options1370 relating to tab-over functionality.

Immediate-access keys and hotkeys are customized using methods similarto those used for customization of tab-over functionality. For example,in one instance of an order entry application component, a userinterface element is configured to respond to a Ctrl-D hotkeycombination by changing the state of submit checkbox 1335 (FIG. 13A) andgenerating a request for the next application user interface 255 (FIG.2). In this instance JavaScript designed to handle the Ctrl-D keycombination is generated using configuration data 440 (FIG. 4) and/orpersonalization data 473 along with the metadata associated withcustomized application user interface 255. Through a similar approach, aCtrl-T immediate-access keystroke combination may be designated tochange the focus from any other element to address field 1350.

The present invention provides significant customization of the ways inwhich data is presented to a user and the ways a user can interact withan application. For example, in one embodiment the stylistic propertiesof tables (grids) are customized. These stylistic properties includecolumn titles, column widths, and similar aspects. In some embodimentscustomization of tables includes column order, sorting by a specificcolumn, display of selected columns, and determination of the number ofrows and/or columns to display.

FIG. 14A illustrates an embodiment of application user interface 255(FIG. 2) including a table 1410 showing the results of a query. Table1410 includes multiple data rows 1420A-1420P and a customized menu bar1430 with find command 1440, view all command 1450, and other navigationcommands 1460 associated with the table. The commands included incustomized menu bar 1430 are optionally selected using configurationinterface 275. Menu bar 1430 is an example of an application componenttypically found in a library of application components accessed in step50 (FIG. 1). The number of rows 1420 shown on a single application userinterface 255 is customizable. Since the number of rows in a table 1410is often more than is convenient to display on a single user interface,the table 1410 may be distributed across several application userinterfaces 255. Navigation between these user interfaces is accomplishedusing navigation commands 1460.

FIG. 14B illustrates an interface 1470 that is included in variousembodiments of IDE 235, configuration interface 275, and user profileinterface 270. Interface 1470 includes an occurs count field 1480 whosevalue determines the maximum number of rows 1420 displayed in aninstance of application user interface 255. Interface 1470 also includesan unlimited occurs checkbox 1490. If this box is checked all availablerows 1420 will be displayed on one application user interface 255 whenthe data is displayed. The configuration of table 1410 specified usinginterface 1470 is retained and used when application user interface 255is revisited. Thus, a state of the customizable view all commandpersists between the present and any subsequent uses of application userinterface 255.

The View All command 1450 (FIG. 14A) is a default aspect of menu bar1430 when all rows 1420 in table 1410 are not visible in a singleinstance of application user interface 255 and instead are distributedover several instances of application user interface 255. FIG. 14Cillustrates the result of executing the View All command. In thisinstance all of rows 1420 in table 1410 are shown in a singleapplication user interface 255. These include rows, such as row 1420Q,not shown in the instance of application user interface 225 illustratedin FIG. 14A.

The number of rows 1420 (or columns) visible in an embodiment ofapplication user interface 225 is resolved in presentation step 150(FIG. 1). In step 150 application server 309 has access to all rows 1420and a value is retrieved from DBMS server 245 to determine which of rows1420 should be displayed in a particular instance of table 1410. Thisvalue is optionally retrieved from configuration data 440 orpersonalization data 473. In a typical embodiment all rows 1420 aretemporarily cached in web application server 305 for immediate access.

The find command 1440 of menu bar 1430 (FIG. 14A) takes advantage of theaccess that application server 309 has to all rows 1420. Since thisinformation is available, even though not displayed, the find commandcan search across all rows, including those that are not shown in thecurrent interface 225. For example, in one embodiment a query returns alist of 100 results and occurs count field 1480 (FIG. 14B) is set to 20.When the results are returned, the first 20 rows 1420 are shown in table1410. A user can use find command 1440 to search all 100 rows D returnedby the query, even if all results are not displayed on the current userinterface. If the find command 1440 locates a result that is not shownin the current table 1410 a new application user interface 225 isgenerated that includes a new table 1410 with the found record. The findoperation typically operates on the copy of all rows 1420 cached in webapplication server 305. The scope over which find command 1440 searchesis user customizable. A user may choose to search over all rows, a fixednumber of rows or only those rows displayed.

An optional sort operation takes advantage of the copy of all rows 1420cached in DBMS server 245 in a manner similar to find command 1440. Forexample, in one embodiment of table 1410 a column heading 1495 isselected to display rows 1420 sorted by that column. The invention isable to perform this sort and display a new instance of table 1410quickly by using the cached copy that includes all rows 1420.

An embodiment of the invention includes customization of the interactionmodels used for communication between internet application system 250and the client displaying application user interface 255. Thesecommunications include complete delivery of user interfaces, web pages,user input from the client, and other messages between the client andweb application server 305.

FIG. 15 illustrates one interaction model wherein data entered by a useris immediately transferred to internet application system 250. In adeliver requested page step 1510 application user interface 255 isdelivered to the client. This application user interface 255 includesdata entry elements such as text entry fields, check boxes, radiobuttons, and the like. In a data entry step 1520 a user enters data intoone of the data entry elements. This data entry includes entering text,changing a check box or radio button, or the like. In a change focusstep 1530 the focus on the current user interface is changed to a userinterface element other than the one used for data R entry in step 1520.The change of focus indicates that data entry step 1520 is completed. Ina transfer data step 1540 the user-entered data is transferred, usingstandard network protocols, to internet application system 250. In anoptional process data step 1550 the transferred data is processed byinternet application system 250. This processing includes actions suchas range checking, delivery to application engine program 440,authentication, and the like. The processing optionally results in aresponse from internet application system 250 that is returned toapplication user interface 255. For example, if a value entered by auser is outside of an allowed range, an error message can be generatedand sent to application user interface 255. Communication betweenapplication user interface 255, internet application system 250, andapplication server 309 can take a significant amount of time, thusslowing the data entry processes. Typically the page delivered in step1510 includes several data entry elements. The steps 1520 through 1550are repeated for each element until the data entry process is completed.If data entry is complete then a new page is requested in an optionalrequest page step 1560.

FIG. 16 illustrates an alternative interaction model whereincommunication between application user interface 255 and internetapplication system 250 is deferred. In this model steps 1510 through1530 are performed in a manner analogous to the steps illustrated inFIG. 15. After change focus step 1530 the process returns to step 1520unless a refresh has been requested. A refresh is specifically requestedby a user, for example, by clicking a “refresh” button. A refresh isalso initiated when a user requests a new user interface or when a usercompletes entering data in a user interface element or applicationcomponent incorporating the interaction model illustrated in FIG. 15.User interface elements on a single instance of application userinterface 255 optionally use different interaction models. If a refreshrequest is received then data is transferred between application userinterface 255 and internet application system 250 in a transfer datastep 1610. The data transferred in step 1610 includes data entered sincethe last data transfer between application user interface 255 andinternet application system 250. The data may, therefore, include dataentered into several data entry elements. In a step 1620, the datatransferred in step 1610 is optionally processed by internet applicationsystem 250 in a manner analogous to step 1550 (FIG. 15). A next page isrequested in an optional request page step 1560.

The “immediate” interaction model illustrated by FIG. 15 typicallyrequires more frequent communication between application user interface255 and internet application system 250 than does the “deferred”interaction model illustrated by FIG. 16. Consistent users may,therefore, prefer the deferred interaction model. However, the immediateinteraction model allows more immediate recognition of errors in dataentry than does the deferred interaction model. Casual users may,therefore, prefer the immediate interaction model.

One embodiment of the invention allows users to choose between these twointeraction models. This choice includes customization (choice of model)by element, by type, by individual application user interface 255, byuser, by application component, or by internet application.

FIG. 17A illustrates an embodiment of configuration interface 275arranged to allow customization of the interaction model used by anapplication component. A processing mode menu 1710 includes aninteractive radio button 1720, a deferred radio button 1730, and anallow expert entry check box 1740. If the deferred radio button 1730 isselected, the deferred interaction model is used for the applicationcomponent. Customization at the component level is subject tomodification via further customization of more specific elements, suchas individual application user interfaces 255 and user interfaceelements, within the component. If interactive radio button 1720 isselected the immediate interaction model is used for the component. Whenthe interactive radio button 1720 is selected the allow expert entrycheckbox is also available for checking or un-checking. If checked, thencomponent interfaces of this application component will include anoption that allows a user to change the interaction model while theinternet application is running. An example of this option isillustrated in FIG. 17B.

FIG. 17B illustrates an instance of application user interface 255 forentering address data. An expert entry checkbox 1760 allows users tochange the interaction model from “Expert Entry” (immediate) to“Standard Entry” (deferred) during execution of the internetapplication. The expert entry checkbox is an embodiment of aninteraction model control command. Checking the expert entry checkbox1760, which has an effect similar to selecting the deferred radio button1730 (FIG. 17A) in a page development step 100, configuration step 110,or personalization step 130, places application user interface 255 inthe Expert Entry mode. For example, in the Expert Entry mode, enteringan invalid date (such as a date in the future) in date entry field 1770does not immediately result in an error message when the user moves theuser interface focus to the text entry field 1780. The error message isnot displayed because the business logic routine, designed to check foran invalid date, is not invoked until a submit checkbox 1790 is checked.In contrast, the Standard Entry mode is used if the expert entrycheckbox 1760 is not checked and the interactive radio button 1720 (FIG.17A) is not selected. In this mode an error message is immediatelydisplayed when an improper date is entered in date entry field 1770 andfocus is changed from date entry field 1770 to, for example, text entryfield 1780.

The systems and methods of the present invention are used to customizeother aspects of internet applications. For example,“Internationalization” includes alternative currencies, date formats,time calculations, and text language. Aspects of internationalizationsuch as these are customized in methods similar to those used forconfiguration of other user interface elements. In another example, userinterface elements are adjusted to conform to the Americans withDisabilities Act. These adjustments include increases in user interfaceelement size, changes in text size, and optimized cursor placement thatreduces the effort required for a user to navigate a user interface.They are also used to adjust application user interface 255 to be moreamenable to screen reading software.

Embodiments of the present invention include customization of errormessages, warnings, and confirmation messages. For example, a consistentuser may prefer to see only critical error messages. In contrast acasual user may prefer to also see hints, warnings and confirmationmessages. Configuration system 225 and personalization system 220 areused to select from among various message options that determine thetypes and importance of messages shown to a user. In one embodimentusers can personalize their interaction with the internet application byselecting among several alternative “message levels.” These levelsinclude, for example, a “show all messages” option, a “show importantmessages” option, and a “show only critical messages” option. Referringagain to FIG. 10B, an example is illustrated in which a user can selectto see confirmation messages when saving data. If a save confirmationproperty 1060 is selected, the user will receive a confirmation whendata has been saved.

The new approach to designing, implementing, and using user interfacesdescribed herein introduces a new model for customization of internetapplications. This customization is accomplished within anHTML/JavaScript environment and therefore is only dependent on a clienthaving standard browser compatibility. The customization is independentof browser add-ons, such as plug-ins or downloaded Java applets orActiveX controls, and also independent of the client-side environment,such as operating system, processing capabilities, or memory, that arebeyond what is required to support the standard browser compatibility.The customization includes modification of user interface elementfunctionality and is thus of significant benefit to consistent users.Various embodiments of the present invention include the use ofcustomization in user interfaces used for communication between a userand an internet application.

Several embodiments are specifically illustrated and/or describedherein. However, it will be appreciated that modifications andvariations are covered by the above teachings and within the scope ofthe appended claims without departing from the spirit and intended scopethereof. For example, the various computer systems described herein maybe implemented as distributed systems; likewise the location of specificdata records is optionally varied among a variety of alternativelocations. The use of “user interface” or “web page” to describe an HTMLbased interface is not meant to restrict the interface to distributionover the World Wide Web or any other specific network. Likewise, an“internet” application is not meant to restrict use of the presentinvention to applications using the Internet or World Wide Web. Aninternet application includes applications designed to execute overnetworks, such as intranets, extranets, wide area networks, or the like,that use communication protocols compatible with a standard browser. The“user” interacting with or using aspects of the present invention may bea person, or alternatively may be another computing system or program.Properties selected as being customizable, and later customized, mayapply to any aspect of an internet application and are not restricted tothose properties of individual user interface elements shown in thevarious figures. Customization of “Keystrokes” as described herein isoptionally extended to include customization of mouse buttons, touchscreens, or alternative data entry systems. Likewise, functionality suchas tab-over need not be tied to a specific button, key or keystrokecombination, such as the “Tab” key. Rather a customizable property mayinclude a response to any user input device.

Microsoft Windows®, Microsoft FrontPage®, ActiveX®, Visual Basic® andMicrosoft Internet Explorer® are registered trademarks of MicrosoftCorporation. Java® and JavaScript® is a registered trademark of SunMicrosystems, Inc. Tuxedo is a registered trademark of BEA Systems, Inc.WebSphere is a registered trademark of International Business Machines,Corporation. PeopleCode and PeopleSoft are registered trademarks ofPeopleSoft, Inc.

1. A customizable application system comprising: an applicationexecution system configured to support an intenet application; a userinterface generator operable to generate an application user interfaceincluding a user interface element, the application user interface beingconfigured as an interface between the internet application and a clientand being configured for delivery to the client over a computer network,the user interface element including a find command that is usercustomizable with respect to a scope of data to be searched, the scopeof data to be searched customizable to include one of all results of apreviously-executed query, a subset of the results of thepreviously-executed query, and only the results of thepreviously-executed query that are displayed in the application userinterface; metadata characterizing the find command; a data repositoryincluding a data record further characterizing the find command, thedata record being user modifiable in response to receiving input from aconsistent user defining a property for the user customizable findcommand and being accessible using the metadata, the property specifyingthe scope of the data to search, wherein the application user interfaceis automatically generated in response to a request from the client andconfigured with the property for the find command, wherein the userinterface is operable to display an amount of data in response to thepreviously-executed query, and wherein the find command is operable toexecute a search within the scope of data with respect to the result ofthe previously-executed query, said executed search including steps of:displaying said subset query results in said application user interface,operating said application user interface independently from a databaseserver, and providing said database server independently from the numberof query operations required to retrieve a requested query result toallow a consistent user to include configuration data andpersonalization data in said generated application user interfacewithout modification of the user interface design developed in pagedevelopment.
 2. The customizable application system of claim 1, whereinthe application user interface is configured for display at the clientusing standard web browser protocols without requiring additionalclient-side application software and without requiring the emulation ofan existing user interface.
 3. The customizable application system ofclaim 1, further including a personalization system configured to modifythe data record.
 4. The customizable application system of claim 1,wherein the application user interface is configured for display at theclient using features of a web browser, the features not requiring abrowser add-on, plug-in, or extension.
 5. The customizable applicationsystem of claim 1, wherein the find command is configurable according toan identity of the client or to an identity of a user.
 6. Thecustomizable application system of claim 1, further including means forgenerating the application user interface using the metadata.
 7. Thecustomizable application system of claim 1, further including anapplication server configured to support the internet application. 8.The customizable application system of claim 1, further includinganother application user interface having the find command, wherein thedata record is configured to characterize the find command in both theapplication user interface and the other application user interface. 9.The customizable application system of claim 1, wherein a customizablestate of the find command persists from one use of the application userinterface to another use of the application user interface.
 10. Thecustomizable application system of claim 1, wherein the client is awireless system.
 11. A computer readable medium including an internetapplication, the internet application comprising: metadata defining anapplication user interface, the application user interface including auser interface element with a user customizable find command, theapplication user interface configured for delivery to a client andconfigured to operate as an interface between a consistent user and theinternet application, the user customizable find command beingcustomizable with respect to a scope of a search, the scope of thesearch being customizable to include one of all results of apreviously-executed query, a subset of the results of thepreviously-executed query, and only the results of thepreviously-executed query that are displayed in the application userinterface; a user interface generator configured to generate theapplication user interface in response to a request from the consistentuser using a user modifiable data record stored in a location physicallyremote from the client, the user modifiable data record configurable tocharacterize the user customizable find command; and a configurationsystem configured to receive an input from a consistent user to modifythe user modifiable data record with a property for the find command,the property specifying the scope of the search, wherein the applicationuser interface is automatically generated and configured with theproperty for the find command, wherein the user interface is operable todisplay an amount of data in response to the previously-executed query,and wherein the find command is operable to execute a search within thescope of search with respect to the results of the previously-executedquery, independently from a database server, said database serverindependent from the type of data stored in the database server and thenumber of query operations required to retrieve a requested query resultallowing a consistent user to include configuration data andpersonalization data in the generated application user interface withoutmodification of the user interface design developed in page development.12. A computer readable medium including an internet application, theinternet application comprising: an application designer moduleconfigured to develop an application user interface, the applicationuser interface including a user interface element with a usercustomizable find command, the application user interface configured fordelivery to a client and configured to operate as an interface between aconsistent user and the internet application, the user customizable findcommand being customizable with respect to a scope of a search, thescope of the search being customizable to include one of all results ofa previously-executed query, a subset of the results of thepreviously-executed query, and only the results of thepreviously-executed query that are displayed in the application userinterface; a user interface generator configured to generate theapplication user interface using a user modifiable data record stored ina location physically remote from the client the user modifiable datarecord configurable to characterize the user customizable find command;a configuration system configured to receive an input from a consistentuser to modify the user modifiable data record with a property for thefind command, the property specifying the scope of the search, whereinthe application user interface is automatically generated and configuredwith the property for the find command, wherein the user interface isoperable to display an amount of data in response to thepreviously-executed query, and wherein the find command is operable toexecute a search within the scope of data with respect to the result ofthe previously-executed query, independently from a database server,said database server independent from the type of data stored in thedatabase server and the number of query operations required to retrievea requested query result allowing a consistent user to includeconfiguration data and personalization data in the generated applicationuser interface without modification of the user interface designdeveloped in page development.
 13. An application execution systemcomprising: means for supporting an internet application; means forgenerating an application user interface using a user modifiable datarecord configured to store data characterizing a user customizable findcommand, the user customizable find command being customizable withrespect to the scope of a search, the scope of data to be searchedcustomizable to include one of all results of a previously-executedquery, a subset of the results of the previously-executed query, andonly the results of the previously-executed query that are displayed inthe application user interface; and means for providing the applicationuser interface to a consistent user, the application user interfaceincluding a user interface element, the application user interfaceconfigured as an interface between the internet application and theconsistent user, the user interface element including the usercustomizable find command, the user interface element configured fordelivery to a client over a computer network, wherein the user interfaceis operable to display an amount of data in response to thepreviously-executed query; and wherein the find command is operable toexecute a search within the scope of data with respect to the result ofthe previously-executed query, operating said application user interfaceindependently from a database server, said database server independentfrom the number of query operations required to retrieve a requestedquery result and independent from the type of data stored in thedatabase server allowing a consistent user to include configuration dataand personalization data in the generated application user interfacewithout modification of the user interface design developed in pagedevelopment.